home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1994.11.gz
/
1994.11
/
000085_kb@cs.umb.edu_Fri Nov 11 01:25:45 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-11-30
|
2KB
Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA14976
(5.65c/IDA-1.4.4 for <tex-k-exp@cs.umb.edu>); Fri, 11 Nov 1994 06:26:55 -0500
Received: by terminus.cs.umb.edu id AA01977
(5.65c/IDA-1.4.4 for tex-k); Fri, 11 Nov 1994 06:25:45 -0500
Date: Fri, 11 Nov 1994 06:25:45 -0500
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199411111125.AA01977@terminus.cs.umb.edu>
To: rl@leeor.technion.ac.il
Cc: comp.text.tex.usenet@decwrl.dec.com
Subject: Re: specifying resolution w/o mode on for dvips
It is true that (as I said above) adding -mode ljfour solves the problem, but
(a) MakeTeXPK has the guessing mechanism builtin, so why not use it, and
Because its guesses aren't necessarily right.
(b) It is harder to explain to the novice what mode is, when he/she just want to
decide whether he/she needs 300 or 600 dpi resolution.
They can't decide that without knowing the mode they want, though.
``300 dpi'' is not enough information to build a font.
I think the right thing is to have a config file 300.ps or something
that says something like
M cx
D 300
then users can say dvips -P300 to get output. Do you buy that?
This happens in my version of the drivers (and not the originals)
because the search paths include the mode as one of the components (by
default). Therefore, the mode must be known on every run, or the right
fonts won't be found. I don't see any way to avoid this -- there is more
than one 300dpi (or 600dpi, or whatever) device in the world.
It should be possible to do better than currently, though, I suppose.
I'll think about it.